An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

I deleted Build 16 from the external Test Flight review approval because I want Build 17 to be used and set up for external review. I successfully removed it and it is not showing up under external testing.. but when I try to add my Build 17, it is greyed out and says that Build 16 is still waiting for review. Can you please fix this as soon as possible so I can begin the review process for my Build 17? Please let me know what information you may need. I'm hoping to get this resolved ASAP.

Hello, I'm looking for advice from developers who have successfully published internet radio applications on the App Store. My app has been rejected multiple times under Guideline 5.2.3 with the following message: "The app provides potentially unauthorized access to third-party audio or video streaming, catalogs, and discovery services." Apple asks me to provide: "documentary evidence evidencing that you have all necessary rights or permissions to the third-party audio or video streaming, catalogs, and discovery services in the app." However, I'm not sure what documentation App Review actually expects. My application works as follows: • It does NOT host, proxy, cache, retransmit, record, convert, or modify any audio streams. • Playback uses Apple's AVPlayer. • Audio is streamed directly from the original broadcaster to the user's device. • The application only retrieves publicly available station metadata and stream URLs from the Radio Browser API. • The app no longer contains any built-in curated station list. • Music identification uses Apple ShazamKit together with metadata lookup (MusicBrainz, Last.fm and Apple iTunes Search API). These services are used only for metadata and artwork, not for streaming audio. I have already contacted the Radio Browser maintainers asking whether they can provide written permission or an official statement, but I have not yet received a reply. My questions are: Has anyone successfully published an App Store internet radio application that uses the Radio Browser API (or another public radio directory)? What documentary evidence satisfied App Review? Does Apple expect permission from the Radio Browser project, or from every individual broadcaster whose publicly available stream is listed in the directory? If your app was approved, what documentation did you provide? Any experience or guidance would be greatly appreciated. Thank you. Has anyone received a successful approval for an internet radio app under Guideline 5.2.3 in 2025 or 2026?

Hello everyone, I’m wondering if anyone has experienced a similar situation. My app is very simple, with no more than five screens. On my first submission, it remained “In Review” for more than 10 days (not “Waiting for Review”), and during that entire time the App Review team never made a decision—no approval, no rejection, and no request for additional information. After waiting that long, I canceled the submission and submitted the app again. It has now been more than one week, and it is still “Waiting for Review” with no progress. I have contacted Apple Developer Support several times. They have escalated the case, and each time I am told that I should receive an update soon. However, I have now been waiting more than 20 days in total, and I still have no decision or meaningful update. Submission ID: 001dd566-c306-477b-856b-639a0fa7cf1b Has anyone experienced this kind of delay? If so, how was it resolved? Any advice or shared experience would be greatly appreciated.

Hello Apple Developer Community / App Review Team, I am writing to ask for guidance regarding an App Review process that appears to be stalled, and also to raise a broader concern about review transparency and communication. I submitted my app for review on July 1, 2026, at around 1:23 PM. As of July 8, 2026, at 2:37 PM, it has been waiting for more than 7 days. During this period, my app appears to have been accessed by three different reviewers. Based on the activity I can see, they entered the app and reviewed it, but the submission status in App Store Connect never formally moved to “In Review.” This creates a difficult situation for developers. It is unclear whether the app is actively being reviewed, stuck in an internal step, waiting for further action, or simply forgotten in the queue. I have been developing for iOS for approximately 7 years, and I have not experienced a review process where it was this difficult to find a clear point of contact or receive a meaningful status update. I have contacted App Store Connect Help multiple times — approximately 3 or 4 times — but I have not received an email response. I have also tried reaching out through other public and professional channels, including LinkedIn and X, not to create pressure, but because I could not find a reliable way to understand what is happening with the submission. My concern is not only about one app or one review delay. I believe this is also an operational issue that affects the broader Apple developer ecosystem. A more transparent, accessible, and trackable App Review process would benefit both developers and Apple users. When developers have clearer visibility into review timelines and status transitions, they can plan releases better, respond to users faster, fix issues more responsibly, and ship higher-quality products. This directly improves the experience of people using Apple products every day. I would appreciate clarification on the following: Is it expected that reviewers may access an app before the submission status changes to “In Review”? What does it mean when reviewer activity is visible, but App Store Connect does not reflect an active review state? Is there currently a backlog or operational delay affecting App Review timelines? What is the recommended path for developers when a submission appears to be stalled for more than 7 days with no response from App Store Connect Help? Are there any planned improvements to make App Review status transitions more transparent, predictable, and easier to follow? Apple holds developers to high standards, which is understandable and valuable for the platform. At the same time, developers need a process that is easier to track, easier to understand, and more responsive when something appears to be stuck. I would appreciate any guidance from Apple or the developer community on how to proceed with this specific review, and I hope Apple continues improving communication and visibility around App Review operations. Respectfully.

Hello Apple Team, Why Is Apple Forcing Us to Use Its In-App Payment System? I am writing this as the CTO & Co-Founder of BS Fintech Pvt. Ltd., India, who is deeply disappointed with our experience over the past six months. Our fintech app, ScoreUp, has been live on the Google Play Store, where it has been serving customers successfully with 99.99% uptime and excellent user feedback. We have invested years of effort in building a reliable product that fully complies with Indian regulations. However, despite multiple submission attempts over the last six months, Apple App Store approval has not moved forward because we are not using Apple's In-App Purchase (IAP) system for subscriptions. This raises an important question: Why are developers forced to use Apple's payment system instead of being allowed to use compliant third-party payment providers? In India, we already work with trusted payment gateways that support UPI and comply with all RBI and NPCI guidelines. These providers process a ₹99 subscription for approximately ₹0.30 per transaction. In comparison, Apple's commission of up to 30% on the same subscription creates a significant financial burden, particularly for startups building affordable subscription-based products. Apple cannot force us to use its payment gateway, which is significantly more expensive than other compliant payment solutions. We strictly adhere to all applicable regulations and compliance requirements prescribed by the Government of India, RBI, and NPCI. Our intention is not to bypass any regulations but to use a fully compliant and cost-effective payment solution that best serves the Indian market. We simply want the freedom to choose a payment solution that is: Fully compliant with Indian laws and regulatory requirements. Cost-effective for our business and our customers. Better suited to the Indian payments ecosystem. Startups invest enormous time, capital, and effort into building innovative products. Restricting app distribution because a developer chooses a compliant third-party payment provider creates a significant barrier for businesses trying to innovate and compete. I would sincerely appreciate clarification from Apple on the following: Why can't our app be approved while using a fully compliant third-party payment gateway? How does this requirement support fair competition and developer choice, particularly in markets like India with a mature, regulated digital payments ecosystem? We hope Apple will continue supporting developers by providing greater flexibility and recognizing regional payment infrastructures that are already secure, regulated, and widely adopted. We look forward to a constructive dialogue and a fair resolution. I request a prompt response and a clear resolution to this matter. You may contact me. If this issue cannot be resolved satisfactorily, I will have to explore all available legal remedies to protect our business interests, including seeking appropriate compensation for the business losses we believe have resulted from this policy and its impact on our app's launch in India.

Hello Apple Support Team, My app's new In-App Purchase appears to be stuck in the review process, and I'd like to check whether there might be an issue with the submission. App Information App Name: Foxify AI - Make Your Own Song Apple ID: 6761515837 Item for Review: New Consumable In-App Purchase Timeline Submitted: July 3, 2026, at 6:28 PM As of today (July 8), the In-App Purchase has remained in "Waiting for Review" for 6 days. Context: We submitted a new app build together with this new In-App Purchase so the Apple Review team could test the updated purchase flow and the new consumable IAP. The app build has already been approved and is currently Pending Developer Release, but the new In-App Purchase is still showing Waiting for Review. Since the IAP has not been approved yet, we are unable to release the new version as planned, and our launch date is approaching. Normally, our In-App Purchases are reviewed within 1–2 days, so this delay seems unusual. Could you please help check whether there is any issue with this submission and, if possible, assist with reviewing it as soon as possible? Any guidance or assistance would be greatly appreciated. Thank you for your support.

Hi everyone, I’m looking for guidance because I’m struggling to understand an App Review decision. My app, The Leaf Cellar, is a cigar companion app that includes cigar image scanning, humidor management, cigar journals, tasting notes, lounge discovery, and recommendations. My app was rejected, yet there are multiple applications currently on the App Store with substantially similar functionality, including: Ember: AI Cigar Companion (released this year) My Humidor – Cigar Journal Humidor Journal Pro ACJ These apps continue to receive updates and remain available on the App Store. I’m trying to understand what materially distinguishes my implementation from theirs. If Apple considers my app to violate a specific guideline, I would appreciate understanding what objective difference exists between my app and these already approved apps. Has anyone experienced a similar situation where comparable apps were approved but theirs was rejected? Were you able to resolve it through App Review or the App Review Board? Any advice on how to present the strongest case would be greatly appreciated. I’m not looking for speculation or opinions. I’m looking for a clear explanation of how the App Store Review Guidelines are being applied in this case, especially given that a competing app with substantially similar functionality was approved and released this year. From my perspective, the current outcome appears inconsistent, and I would appreciate any insight from developers who have successfully navigated a similar situation. Thank you.

Our app has been in review for over a month with no status change or communication from App Review. Typical reviews clear within 24–48 hours, so this is well outside the normal window. Can anyone from App Review advise on next steps or escalate? App details and submission ID available on request. Thanks.

Is anyone else seeing their app waiting for review for more than a few days? I submittit mine 4 days ago. I thought it usually takes about 1-3 days. Just curious if that is something everyone is seeing right now?

Hey everyone! I recently submitted a build to TestFlight and am currently waiting for it to be approved for external testing. It’s been over 4 days since I submitted the build, and while online it says that builds are reviewed within 24-48 hours, it’s been over 48 hours now. I’m curious if anyone else has experienced a similar delay.

I recently noticed that an app called Private Browsing Web Browser has been ranking at the top for the keyword “browser” on the App Store for a long time, even ahead of well-known browsers like Chrome, Firefox, and Safari. This is not only the case in the U.S.; it also appears to rank top in many other regions. This app has not been updated for a long time, and both its interface and feature set seem extremely basic. There also appears to be nobody to discuss it on the internet, and some of the App Store ratings look very suspicious. I previously reported this to the Apple team by email, and questioning about the algorithm, but they consistently responded: The App Store ranking system has no problem, and it's working as expected.” I wanted to ask everyone: Do you think it is normal for this app to rank number one for “browser” on the App Store? Also, the same developer has another very similar browser app called Snowbunny Private Web Browser, which also ranked high.

Hello, My app Jewel Coloring+ Sort Beads IQ+ (App ID: 6785241915) appears to be stuck in the App Review process, and I would like to check whether there may be an issue with this submission. The current version was originally planned for release on June 30, 2026. However, today is July 7, 2026, and the app is still in "Waiting for Review." Current status: Waiting for Review No messages in Resolution Center No requests for additional information We have also submitted multiple Support inquiries but have not received any response so far. This version is particularly important to our team, as it is tied to a planned release schedule and user acquisition activities that had already been prepared in advance. Given the unusually long delay, we are unsure whether the submission is proceeding normally or if there may be an issue requiring attention. If an Apple staff member could help check the status of this submission, it would be greatly appreciated. Thank you for your time and assistance.

Hello, My app Jewel Coloring+ Sort Beads IQ+ (App ID: 6785241915) appears to be stuck in the App Review process, and I would like to check whether there may be an issue with this submission. The current version was originally planned for release on June 30, 2026. However, today is July 7, 2026, and the app is still in "Waiting for Review." Current status: Waiting for Review No messages in Resolution Center No requests for additional information We have also submitted multiple Support inquiries but have not received any response so far. This version is particularly important to our team, as it is tied to a planned release schedule and user acquisition activities that had already been prepared in advance. Given the unusually long delay, we are unsure whether the submission is proceeding normally or if there may be an issue requiring attention. If an Apple staff member could help check the status of this submission, it would be greatly appreciated. Thank you for your time and assistance.

HI all, My app was live for several months then I got an email saying my developer account was banned for fraud (To be honest I am not sure if I had even submitted an update or whether they just hit me out of the blue) `Evidence of Dishonest or Fraudulent Activity App submissions from your account have engaged in concept or feature switch schemes to evade the review process, such as dynamically populating different app content after review, submitting apps with hidden features, repeatedly submitting misleading apps, and/or submitting apps with concrete references to content that you are not authorized to provide or is otherwise not appropriate for the App Store.` Anyway, my suspicion is we had just flagged some auto detection script, and I appealed immediately stating we had no such hidden code or features, we are a simple flutter app backed with firebase, no paywall pages or anything like that. Anyway, its now been 30 days with no response, I have heard not to try and message them again as it may reset our place in the queue, so I am just wondering what to do at this stage? I have had to pause our paid ads, and its a bad look for us right now with a broken apple link on our website. This is the only app I have on my developer account. APP ID: 6763960507

Hello, I'm evaluating Foundation Models announced at WWDC 2026 and have a question regarding App Store distribution. My understanding is that Foundation Models are only available on supported devices and operating system versions. For apps that rely on Foundation Models as their primary functionality (rather than offering AI as an optional feature), I'm trying to understand the recommended distribution strategy. Currently, iOS provides Required Device Capabilities to prevent users from installing apps that require hardware features such as GPS, ARKit, or NFC. However, I couldn't find an equivalent Required Device Capability for Foundation Models. I also couldn't find a way to limit App Store availability by supported device models. My questions are: What is the recommended way to distribute an app whose primary functionality depends on Foundation Models? Is there currently any supported mechanism to prevent users with unsupported devices from downloading such an app? Is Apple planning to introduce a Required Device Capability (or a similar App Store filtering mechanism) for Foundation Models before public release? Without such a mechanism, users may be able to install the app successfully but then discover that its primary functionality is unavailable on their device. I'd appreciate any guidance on the recommended approach. Thank you.

Hi everyone, I’m currently experiencing unusually long review waiting times and wanted to ask if others see the same behavior this week. My situation: • App Store update has been in “Waiting for Review” significantly longer than usual • A newly submitted build seems stuck • TestFlight processing is slower than I normally see • Expedited review request and contact attempts didn’t change the status so far What confuses me is that I still see other apps receiving updates, so I’m unsure whether this is a broader review delay or something submission-specific. I’m not trying to escalate anything — just looking to understand if this is currently affecting more developers. Would really appreciate hearing about your recent experiences. Thanks and good luck to everyone waiting 🙂

Hello, Our GAKO Business update has been repeatedly delayed in “Waiting for Review,” despite multiple contacts with Apple Developer Support and an approved expedited review request. App: GAKO Business Version: 1.3.1 Current submission date: July 3, 2026 Current status: Waiting for Review Expedited review: Approved This issue has been ongoing across multiple submissions for approximately one month. We have contacted Apple Developer Support several times and followed up repeatedly under the same support case. However, the current submission has still not entered review. The update contains critical production fixes affecting existing App Store users. GAKO Business is used by real businesses to manage appointments, employees, schedules, services, and customer records. The currently published version contains issues affecting essential business workflows, while the corrected version remains unavailable. Apple has confirmed that the application was placed in the expedited review queue. However, it remains in “Waiting for Review.” We are not asking Apple to bypass the App Review Guidelines. We would like Apple to verify whether the submission is affected by an internal routing issue, technical hold, or another submission-level problem. Has anyone experienced the same situation where expedited review was approved, but the application remained in “Waiting for Review”? If Apple staff sees this post, we would greatly appreciate assistance in checking the submission. Thank you.

Hi at all,I just published a new version of our application selecting the option "Reset rating when this version is released".The problem is that, even if the application is now available on the apple store the old rating is shown.Any suggestions?Regards,Enzo.

Hi everyone, I’m currently stuck with a blocking issue in App Store Connect and would really appreciate any guidance or insight. Issue: My app version (iOS App 1.0) is missing the “In-App Purchases and Subscriptions” section entirely. Because of this, I cannot attach my subscriptions to the version, which is preventing me from submitting the app for review. Additionally, I also do not have the option to create a new version, so I can’t work around the issue by moving to 1.0.1. What happened before this: I uploaded a build (Build 24) Submitted the app for review Then removed the submission After that, the IAP section disappeared completely Since then, I cannot attach subscriptions or create a new version Current state: Subscriptions are created and show “Waiting for Review” New Build is attached to Version 1.0 All metadata and screenshots are complete “In-App Purchases and Subscriptions” section is missing “Add Version” option is not available What I’ve tried: Removing and re-adding the build Waiting for UI refresh/processing Contacting Apple Developer Support (case has been escalated for 6 days with no response) Impact: This is currently blocking my app launch because I would be rejected since the subscriptions are not linked, as I cannot submit my first subscription with the app. Questions: Has anyone experienced a missing IAP section after removing a submission? Is there any way to force reset the app version state from the developer side? Is this a known App Store Connect issue? Any help or suggestions would be greatly appreciated. Thanks in advance.

Hello, I have a blocking issue in App Store Connect. I need to submit my In-App Purchase together with the app (first-time approval), but: The option to attach In-App Purchases is missing I cannot create a new app version I cannot properly edit the current version This creates a deadlock and prevents me from submitting the app correctly. This does not seem like a configuration issue, but a problem in App Store Connect. Has anyone experienced this or knows how to resolve it? Thank you.